home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
e
/
misc.txt
/
000110_fdc@panix.com_Tue Aug 7 13:34:22 2007.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Path: reader2.panix.com!panix!not-for-mail
From: Frank Da Cruz <fdc@panix.com>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Building C-Kermit-8.211
Date: Tue, 7 Aug 2007 17:09:48 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 37
Message-ID: <slrnfbh9qr.91j.fdc@panix3.panix.com>
References: <1186026072.470873.303570@q75g2000hsh.googlegroups.com>
Reply-To: fdc@columbia.edu
NNTP-Posting-Host: panix3.panix.com
X-Trace: reader2.panix.com 1186506588 17170 166.84.1.3 (7 Aug 2007 17:09:48 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Tue, 7 Aug 2007 17:09:48 +0000 (UTC)
User-Agent: slrn/0.9.8.0 (NetBSD)
Xref: panix comp.protocols.kermit.misc:15681
On 2007-08-02, <gregg.drwho8@gmail.com> wrote:
: While building the lastest release of C-Kermit from source retrieved
: several days ago from the site, my laptop who's running Slackware-7.1,
: old but works well on older gear, the process decided to crash
: complaining about a typo. It was regarding the definition of a term,
: regarding the crypt libraries.
:
: However trying it again, this time extracting into a fresh directory
: it didn't happen. Instead I get a normal build. I can present a
: script file of the process for those that are interested.
:
As far as I know, the "make linux" target should be fine everywhere.
It is perhaps the most "advanced" target in the makefile, as it includes
a number of tests to allow for different Linux variations. I can't explain
why trying to build it once would crash (what crashed exactly?) and doing
it again worked ok, but if you wish, please go ahead send the script to
kermit-support@columbia.edu.
: And here's something strange. In the interim I grabbed a binary,
: thinking I would use that if I couldn't get a good build made. Instead
: it complains about missing symbols in the libraries. That message I
: don't have, because I discarded the binary after building the working
: one. What is interesting to note is that the laptop is wearing the
: latest series of patches that were available at the time the
: distribution was released, and the issues were of course identified.
:
: These were complaints about the Glibc signatures found in the runtime
: libraries. Can one of you at the Kermit place check the dates of your
: installed Glibc kits and advise me accordingly? Again this concerns
: Slackware-7.1.
:
Kermit binaries -- and this is probably true of most other applications as
well -- are vulnerable to this kind of thing, in Linux especially. It is
always better to build it on the computer where it is to be run, to allow
for library differences and so on.
- Frank